Systems and methods for warranty coverage alerts based on acquisition data

ABSTRACT

A computer-implemented method for facilitating identification of object coverage information using prior acquisition data, that includes detecting an object acquisition, determining a grouping of the object acquisition from a plurality of groupings, and identifying a corresponding object acquisition within the same grouping as the object acquisition. The method further includes determining the corresponding object acquisition includes coverage protection, and transmitting an alert of the corresponding object acquisition and the coverage protection.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally to asystem for facilitating identification of object coverage information,and relate particularly to methods and systems for generating alerts ofthe existence of coverage protection for an object acquisition based onprior acquisition data of a user.

BACKGROUND

Acquisitions (e.g., purchases) of certain products by consumers may beassociated with, or accompanied by, a warranty plan that providescertain protections to the consumer. For example, a warranty play mayafford a reimbursement benefit to the consumer from enduring financialcosts in certain circumstances, such as from a loss or damage to theacquired product. However, despite having access to such protectionbenefits, a consumer may disregard, fail to recall, or lack knowledge ofthe existence of the warranty plan covering the product. Accordingly,the consumer may relinquish the benefits afforded by the warranty planwhen conducting subsequent transactions to acquire a replacement for theproduct and/or expenditures to repair the product.

The present disclosure is directed to addressing one or more of theseabove-referenced challenges. The background description provided hereinis for the purpose of generally presenting the context of thedisclosure. Unless otherwise indicated herein, the materials describedin this section are not prior art to the claims in this application andare not admitted to be prior art, or suggestions of the prior art, byinclusion in this section.

SUMMARY

According to certain aspects of the disclosure methods, systems, andnon-transitory computer-readable media are disclosed for generatingalerts of applicable coverage protection for an acquired object (e.g., aproduct). Each of the examples disclosed herein may include one or moreof the features described in connection with any of the other disclosedexamples.

In one example, a computer-implemented method for facilitatingidentification of object coverage information using prior acquisitiondata, comprising: detecting an object acquisition; determining agrouping of the object acquisition from a plurality of groupings;identifying a corresponding object acquisition within the same groupingas the object acquisition; determining the corresponding objectacquisition includes coverage protection; and transmitting an alert ofthe corresponding object acquisition and the coverage protection.

In another example, a computer-implemented method for automating productcoverage identification, comprising: determining an occurrence of anobject acquisition; categorizing the object acquisition to at least onecategory of a plurality of categories based on a characteristic of theobject acquisition; determining a prior product acquisition includedwithin the at least one category has a corresponding characteristicsimilar to the characteristic of the object acquisition; determining theprior object acquisition includes a coverage plan; and generating anotification including the prior object acquisition and the coverageplan.

In a further example, a system may include a processor, and a memorystoring instructions that, when executed by the processor, causes theprocessor to perform operations including: receiving data indicative ofan object acquisition; determining at least one grouping of the objectacquisition from a plurality of groupings; identifying a matching objectacquisition in the same grouping of the object acquisition from priorobject acquisition data; determining the matching object acquisitionincludes object coverage protection; and transmitting an alert to a userdevice of the matching object acquisition and the object coverageprotection.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 depicts an exemplary client-server environment that may beutilized according to aspects of the present disclosure.

FIG. 2 depicts an exemplary process for transmitting object coverageinformation to a user device.

FIG. 3 depicts an example of a computing device, according to aspects ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

The terminology used in this disclosure is to be interpreted in itsbroadest reasonable manner, even though it is being used in conjunctionwith a detailed description of certain specific examples of the presentdisclosure. Indeed, certain terms may even be emphasized below; however,any terminology intended to be interpreted in any restricted manner willbe overtly and specifically defined as such in this Detailed Descriptionsection. Both the foregoing general description and the followingdetailed description are exemplary and explanatory only and are notrestrictive of the features, as claimed.

In this disclosure, the term “computer system” generally encompasses anydevice or combination of devices, each device having at least oneprocessor that executes instructions from a memory medium. Additionally,a computer system may be included as a part of another computer system.

In this disclosure, the term “based on” means “based at least in parton.” The singular forms “a,” “an,” and “the” include plural referentsunless the context dictates otherwise. The term “exemplary” is used inthe sense of “example” rather than “ideal.” The term “or” is meant to beinclusive and means either, any, several, or all of the listed items.The terms “comprises,” “comprising,” “includes,” “including,” or othervariations thereof, are intended to cover a non-exclusive inclusion suchthat a process, method, or product that comprises a list of elementsdoes not necessarily include only those elements, but may include otherelements not expressly listed or inherent to such a process, method,article, or apparatus. Relative terms, such as, “substantially,”“approximately,” “about,” and “generally,” are used to indicate apossible variation of ±10% of a stated or understood value.

In general, the present disclosure provides methods and systems forgenerating and transmitting object coverage information to a user devicebased on detecting an object (e.g., a good, a service, etc.) acquisitionand identifying a corresponding object acquisition from prioracquisition data that includes coverage protection. An alert may betransmitted with the corresponding object acquisition information andcoverage protection to allow a user to identify and utilize theprotections afforded by the coverage plan. As will be discussed ingreater detail herein, existing techniques may be improved with themethods and systems of the present disclosure.

In some instances, information relating to the availability of coverageprotection may be unknown to the user when initially acquiring anobject, such as when such warranty is provided by the manufacturer ofthe object or the financial service provider that processed anacquisition of the object. Users seeking to minimize instances offoregoing coverage benefits afforded by warranty protection plans forpreviously-acquired objects (e.g., products or services) may requireproactive assistance in identifying the existence of such coverage andthe applicability of protection benefits provided by said plan.Accordingly, a need exists to provide a real-time ability to generateand transmit alerts to a user with coverage protection information whenconducting object acquisitions based on prior acquisition data.

FIG. 1 depicts an exemplary client-server environment that may beutilized with techniques presented herein. For example, the environmentmay include a system 100 with one or more user devices 105, one or morefinancial institution servers 110, one or more merchant servers 120, apurchase data repository 125, and one or more warranty data servers 140.System 100 may further include a transaction processing server 130. Theone or more components of system 100 may communicate with one anotheracross an electronic network 115, and in any arrangement.

It should be appreciated that system 100 may include a plurality ofusers, each of which may include or otherwise be associated with atleast one user device 105. User device 105 may include various suitableapparatuses, including but not limited to, a mobile device, a computer,a wearable device (e.g., a smartwatch) and the like. User device 105 maybe configured to transmit and receive signals between one or morecomponents of system 100, the signals being indicative of a data ormessages relating to an object acquisition (e.g., transaction, purchase,etc.). One or more user devices 105 may include a third-party softwareinstalled thereon for receiving signals from other components of system100. The third-party software may include, but is not limited to, anelectronic application (e.g., a mobile internet application, a textmessaging application, an e-commerce application, a social mediaapplication, or the like), an internet browser extension, or a websitepage. The third-party software on user device 105 may includeprogrammable instructions that cause user device 105 to communicate withthe one or more components of system 100.

The user may be a customer of one or more financial institutions and mayhave one or more consumer accounts with said financial institution(s).In this instance, the one or more consumer accounts may be stored on (orotherwise associated with) financial institution server 110. The usermay conduct one or more transactions with the consumer account(s), suchas, for example, purchasing a product, a good, or a service(collectively referred to herein as “object”) from one or moremerchants, retailers, and the like. Financial institution server 110 mayinclude or be in communication with a purchase data repository 125 forstoring historical financial data, such as, for example, acquisition(purchase) data. In the example, financial institution server 110 isdepicted as a separate component from purchase data repository 125,however, in other embodiments, the financial data may be stored onfinancial institution server 110.

Still referring to FIG. 1 , merchant server 120 may be configured togenerate acquisition data indicative of an object acquisition (e.g.,purchase) made with the consumer account. In some embodiments, theconsumer account may be communicatively coupled to a consumer card(e.g., credit card, debit card, etc.), a mobile payment application(e.g., on user device 105), and the like. Accordingly, completing apurchase may generate the acquisition data thereby indicating anoccurrence of an object acquisition (e.g., transaction). In someembodiments, the acquisition data may include various informationrelating to the transaction.

For example, the acquisition data may include one or more purchasecharacteristics (e.g., data fields) relating to the transaction. The oneor more purchase characteristics may include, but are not limited to, aproduct (e.g., good, service, etc.) name, a merchant name, a transactiondate, a transaction time, a transaction identification number, atransaction amount, a merchant identification number, a merchantcategory code, a product description, a transaction description, animage, and more. Merchant server 120 may be configured to communicatethe acquisition data to financial institution server 110 and/or purchasedata repository 125.

In some embodiments, a user may generate acquisition data relating tothe transaction via user device 105. For example, a user may be promptedby transaction processing server 130 to provide information relating tothe object acquisition at a time of the transaction. In one example, auser may transmit a picture of the acquired object, a receiptdocumenting details of the purchase, etc., taken from user device 105 oranother device in communication with user device 105. In otherembodiments, user device 105 may automatically generate acquisition datarelating to the transaction, such as, for example, in the form of metadata. The meta data may include information defining a location of theuser at the time of purchase, an identification of the user, and more.Purchase data repository 125 may store the acquisition data generated bymerchant server 120 and/or user device 105, and associate the data withthe consumer account of the user.

The object acquisitions conducted by a user for various goods orservices may be associated with one or more warranty coverage plans. Thewarranty coverage plan may provide protection benefits to the user asthe owner of the acquired object, with said protection benefits beinginitiated in response to the acquisition of the object by the user fromthe merchant. In some examples, the warranty coverage plan may beprovided to the user by the financial institution associated with theconsumer account utilized by the user to conduct the object acquisition.In other examples, the warranty coverage plan may be provided by amanufacturer of the object or the merchant from which the object wasacquired. It should be understood that the warranty coverage plan may beautomatically provided to the user by virtue of the acquisition, oracquired (e.g., purchased) by the user separately from the object.

Warranty data server 140 may store coverage information relating to thewarranty coverage plan and the corresponding acquired object associatedwith the warranty coverage plan. It should be appreciated that system100 may include, or be in communication with, a plurality of warrantydata servers 140 across electronic network 115. For example, system 100may include a plurality of warranty data servers 140 from multipleproduct manufacturers, payment service providers, retail serviceproviders, web platform providers, and more.

Transaction processing server 130 may be configured to detect anoccurrence of an object acquisition in response to receiving datacorresponding to the object acquisition from one or more components ofsystem 100. For example, transaction processing server 130 may receiveacquisition data from financial institution server 110 and/or merchantserver 120. Transaction processing server 130 may be further configuredto obtain prior object acquisition data from financial institutionserver 110 and/or purchase data repository 125, and warranty coverageplan information associated with the object acquisition or prior objectacquisitions from warranty data server 140. As described in furtherdetail herein, transaction processing server 130 may be configured totrain a machine learning model to determine that a detected objectacquisition serves as a replacement for a prior object acquisitionconducted by a user, and that the warranty coverage plan from the priorobject acquisition provides protection benefits to the user.

As used herein, a “machine learning model” may include data (e.g.,acquisition data, warranty data, etc.) or instruction(s) for generating,retrieving, and/or analyzing such data. Further, as used herein, a“machine learning model” is a model configured to receive input, andapply one or more of a weight, bias, classification, or analysis on theinput to generate an output. The output may include, for example, aclassification of the input, an analysis based on the input, a design,process, prediction, or recommendation associated with the input, or anyother suitable type of output. A machine learning model is generallytrained using training data, e.g., experiential data and/or samples ofinput data, which are fed into the model in order to establish, tune, ormodify one or more aspects of the model, e.g., the weights, biases,criteria for forming classifications or clusters, or the like. Aspectsof a machine learning model may operate on an input linearly, inparallel, via a network (e.g., a neural network), or via any suitableconfiguration.

The execution of the machine learning model may include deployment ofone or more machine learning techniques, such as linear regression,logistical regression, random forest, gradient boosted machine (GBM),deep learning, and/or a deep neural network. Supervised and/orunsupervised training may be employed. For example, supervised learningmay include providing training data and labels corresponding to thetraining data. Unsupervised approaches may include clustering,classification or the like. K-means clustering or K-Nearest Neighborsmay also be used, which may be supervised or unsupervised. Combinationsof K-Nearest Neighbors and an unsupervised cluster technique may also beused. Any suitable type of training may be used, e.g., stochastic,gradient boosted, random seeded, recursive, epoch or batch-based, etc.

Still referring to FIG. 1 , one or more of user device 105, financialinstitution server 110, merchant server 120, purchase data repository125, warranty data server 140, and/or transaction processing server 130may communicate with each other over the electronic network 115 inexecuting the machine learning model to determine an object acquisitionis a replacement for a prior objection acquisition. Electronic network115 may include a telecommunications network such that one or more ofuser device 105, financial institution server 110, merchant server 120,purchase data repository 125, warranty data server 140, and/ortransaction processing server 130 may communicate with one another overthe telecommunications network. The telecommunications network mayinclude, for example, a telephone network, a cellular network, and thelike. In other embodiments, electronic network 115 may be a publicswitched telephone network (PTSN), a voiceover Internet Protocol (VoIP)network, a wide area network (“WAN”), a local area network (“LAN”),personal area network (“PAN”), or the like.

While FIG. 1 depicts the various components of system 100 as physicallyseparate and communicating across network 115, it should be appreciatedthat in other embodiments one or more components of system 100 may beincorporated partially or completely into any of the other componentsshown in FIG. 1 . Some or all of the functionality of the machinelearning model may be incorporated into one or more components of system100, such as, for example, transaction processing server 130. Some orall of the functionality of transaction processing server 130 may beaccessible via user device 105 and incorporated into a mobile internetapplication, an internet browser extension, or website page.

In some embodiments, one or more components of system 100 (e.g.,transaction processing server 130) may be configured to train a machinelearning model to execute one or more processes, such as, for example,process 200 shown and described herein. As described in further detailbelow, transaction processing server 130 may be further configured totrain the machine learning model to predict one or more variables inaddition to executing the exemplary process 200. The one or morevariables may include a relationship between one or more prior objectacquisitions and a recent object acquisition, and more.

Multiple approaches may be used when predicting the relationship betweenprior object acquisitions and recent objection acquisitions. The machinelearning model trained by transaction processing server 130 may includean automatable, adaptable tool that may provide accurate predictions asto the relationship. In some embodiments, the model trained bytransaction processing server 130 may include using a “base” or standardmachine learning algorithm or technique, and adapting it based on theacquisition data and/or warranty data received from the one or morecomponents of system 100. In such embodiments, a model including a basemachine learning algorithm or technique configured to providepredictions may be trained by transaction processing server 130. Itshould be appreciated that transaction processing server 130 may be oneor more hardware and/or software components that are configured to sortand analyze the data shown and described herein, generate, train, and/ormodify the machine learning model, predict a relationship between objectacquisitions, and determine a recent acquisition serves as a replacementof a prior acquisition using the trained machine learning models.

In some embodiments, transaction processing server 130 may include aplurality of computing devices working in concert to perform dataanalyses and to determine the replacement evaluation. Such computingdevices may be any suitable computing devices, now-known orlater-developed, capable of performing aspects of the processes andmethods described herein. Transaction processing server 130 may belocated in a single geographic area or multiple geographic areas, andmay be connected to one another via, e.g., wired or wireless components(e.g., network 115). System 100 may be programmed in various suitableformats, such as, for example, on a platform of a financial institutionservice provider, a web browser extension, a mobile device application,a payment service provider, and more.

FIG. 2 illustrates an exemplary process 200 for generating an alert withcoverage information of a previously-acquired object based ondetermining the acquisition of a replacement in accordance withembodiments of the present disclosure. It should be understood that thesteps described herein, and the sequence in which they are presented,are merely illustrative such that additional and/or fewer steps may beincluded without departing from the scope of the present disclosure.

Initially, at step 202, financial institution server 110 (and/ortransaction processing server 130) may detect an object acquisition,e.g., an occurrence of a transaction conducted with a consumer account(hereinafter referred to as “present object acquisition”). For example,a transaction may be detected by transaction processing server 130 inresponse to receiving acquisition data indicative of a purchase madewith the consumer account, such as from merchant server 120. In someembodiments, the consumer account may be communicatively coupled to aconsumer card (e.g., credit card, debit card, etc.), a mobile paymentapplication (e.g., on user device 105), and the like. Accordingly,completing a purchase may generate the acquisition data therebyindicating an occurrence of the transaction. In some embodiments, theacquisition data may include various information relating to thetransaction.

For example, the acquisition data may include one or more purchasecharacteristics (e.g., data fields) relating to the transaction. The oneor more purchase characteristics may include, but are not limited to, aproduct (e.g., good, service, etc.) name, a merchant name, a transactiondate, a transaction time, a transaction identification number, atransaction amount, a merchant identification number, a merchantcategory code, a product description, a transaction description, animage, and more.

At step 204, transaction processing server 130 may be configured todetermine whether the object acquired in the transaction (step 202) isassociated with coverage protection. For example, transaction processingserver 130 may analyze the acquisition data to determine whether the oneor more purchase characteristics correspond to objects that routinelyinclude a warranty plan. Transaction processing server 130 maycommunicate with financial institution server 110 and/or warranty dataserver 140 to retrieve acquisition data of previous object acquisitionsconducted by the user and/or a plurality of other users. In thisinstance, the acquisition data of the transaction detected at step 202may be compared to the historical acquisition data of the plurality ofprior acquisitions to determine whether the present object acquisition(step 202) is for an object routinely associated with coverageprotection.

By way of illustrative example only, the object acquired at step 202 mayinclude perishable food such that the purchase characteristics of theacquisition data relating to the transaction may identify the product assuch. In this instance, a merchant name associated with the objectacquisition may identify a grocery store at which the perishable foodwas purchased. A merchant identification number associated with thegrocery store from which the object was acquired, and/or a merchantcategory code classifying the type of business of which the merchant isa part of, may be indicative of a store primarily engaged in retailingfood products. A product and/or a transaction description may furtherdefine the type of good to which the object acquisition relates. Atransaction amount associated with the object acquisition may fallwithin one of a plurality of predefined threshold ranges (e.g., about$1.00 to $100.00, about $101.00 to $200.00, about $201.00 to $500.00,and more), such as about $1.00 to $100.00. It should be appreciated eachof the purchase characteristics may be indicative of the object (e.g.,good or service) acquired by the user at step 202, and may serve as aparameter for transaction processing server 130 determining whether theobject acquisition is associated with coverage protection.

Transaction processing server 130 may be configured to analyzehistorical acquisition data from financial institution server 110 toidentify one or more prior object acquisitions having similar purchasecharacteristics as the object acquisition at step 202. Transactionprocessing server 130 may cross-reference the prior object acquisitionshaving similar purchase characteristics with warranty data server 140 todetermine whether the prior object acquisitions included a warrantyplan. Transaction processing server 130 may assess whether the presentobject acquisition may be associated with coverage protection based ondetermining whether a majority percentage (e.g., 51% or more) of theprior object acquisitions having similar purchase characteristicsincluded a warranty plan. In this instance, transaction processingserver 130 may determine that prior object acquisitions for perishablefood products did not routinely include warranty plans, such that theobject acquisition at step 202 is not associated with coverageprotection benefits. In response to transaction processing server 130determining the object acquisition of step 202 is not associated withcoverage protection at step 204, system 100 may end the process 200.

By way of another illustrative example, the object acquired at step 202may include electronic equipment such that the purchase characteristicsof the acquisition data relating to the transaction may identify theproduct as such. In this instance, a merchant name associated with theobject acquisition may identify a consumer electronics retailer at whichthe electronic equipment was purchased. A merchant identification numberassociated with the consumer electronics retailer from which the objectwas acquired, and/or a merchant category code classifying the type ofbusiness of which the merchant is a part of, may be indicative of astore primarily engaged in retailing electronic appliances. A productand/or a transaction description may further define the type of good towhich the object acquisition relates. A transaction amount associatedwith the object acquisition may fall within one of a plurality ofpredefined threshold ranges (e.g., about $1.00 to $100.00, about $101.00to $200.00, about $201.00 to $500.00, and more), such as about $201.00to $500.00.

Transaction processing server 130 may analyze historical acquisitiondata from financial institution server 110 to identify prior objectacquisitions having similar purchase characteristics, andcross-reference the prior object acquisitions with warranty data server140 to assess whether the present object acquisition may be associatedwith coverage protection. In this instance, transaction processingserver 130 may determine that prior object acquisitions for electronicequipment products did routinely include warranty plans, such that theobject acquisition at step 202 is associated with coverage protectionbenefits. In response to transaction processing server 130 determiningthe object acquisition of step 202 is associated with coverageprotection at step 204, transaction processing server 130 may proceed tostep 206.

Still referring to FIG. 2 , and at step 206, transaction processingserver 130 may be configured to determine an object grouping of theobject acquisition detected at step 202 from one of a plurality ofobject groupings. Each of the plurality of object groupings may includedata indicative of a plurality of prior object acquisitions conducted bythe user performing the object acquisition at step 202. In someembodiments, the plurality of object groupings and the correspondingdata for each of the plurality of prior object acquisitions categorizedwithin each of the object groupings may be stored in purchase datarepository 125.

Transaction processing server 130 may compare the purchasecharacteristics of the present object acquisition with purchasecharacteristics of the prior object acquisitions to determine theparticular object grouping that the present object acquisition belongsin. For example, transaction processing server 130 may determine thatthe object grouping having prior object acquisitions with substantiallysimilar purchase characteristics as the present object acquisition isthe object grouping of the present object acquisition. It should beappreciated that prior object acquisitions may be clustered togetherinto similar object groupings based on the type of products that werepreviously acquired (e.g., cameras, computers, cellular devices,vehicles, audible systems, houseware, kitchenware, furniture, etc.).

At step 208, transaction processing server 130 may be configured toanalyze the purchase history data (e.g., the plurality of prior objectacquisitions) categorized within the particular object grouping of thepresent object acquisition. At step 210, transaction processing server130 may be configured to identify a matching object acquisition withinthe object grouping that relates to the present object acquisition.Stated differently, transaction processing server 130 may search thepurchase history data within the object grouping (step 208) to identitya prior object acquisition conducted by the user for a similar productas that acquired by the user in the present object acquisition (step202). It should be appreciated that transaction processing server 130may determine that a product from a prior object acquisition is similarto that acquired in the present object acquisition from a comparison ofthe respective purchase characteristics of each to one another.

A product from a prior object acquisition may be similar to one acquiredin the present object acquisition when one or more of a product name, amerchant name, an acquisition amount, a product description, atransaction description, or more are alike. In some instances,transaction processing server 130 may determine that a product is thesame despite being different versions, acquired from differentmerchants, produced by different manufacturers, having differentacquisition amounts, and more. Accordingly, it should be appreciatedthat a prior object acquisition conducted by the user may be determinedto be related to the present object acquisition despite includingvarying purchase characteristics.

In response to determining the object grouping does not include at leastone prior object acquisition that relates to the present objectacquisition, transaction processing server 130 may be configured to endthe process 200. Alternatively, in response to determining the objectgrouping does include at least one prior object acquisition that relatesto the present object acquisition, transaction processing server 130 maybe configured to, at step 212, determine whether the object acquired viathe present object acquisition is a replacement for the prior objectacquired via the prior object acquisition. In some embodiments,transaction processing server 130 may generate a verification messagefor transmission to user device 105 (e.g., via electronic network 115)soliciting the user's confirmatory feedback on whether the presentobject acquisition serves to replace a product from the prior objectacquisition. In this instance, user device 105 may transmit an input(e.g., an affirmative or negative response) to transaction processingserver 130 responsive to the inquiry.

In other embodiments, transaction processing server 130 may determinewhether the present object acquisition replaces a prior object using thetrained machine learning model. As described in detail above,transaction processing server 130 may be configured to train the machinelearning model to determine whether an object acquisition is areplacement of a prior object acquisition based on one or more of theacquisition data stored in purchase data repository 125 and the warrantydata on warranty data server 140. In one example, transaction processingserver 130 trains the machine learning model to categorize or disregardfuture object acquisitions as replacements of prior object acquisitionsbased on a frequency of the transactions relative to one another. Forexample, transaction processing server 130 may determine that the userroutinely acquires objects having similar purchase characteristics asprior object acquisitions, such that the machine learning model may betrained to determine the future object acquisitions do not serve asreplacements given a regularity of the repetitive acquisitions.

In another example, transaction processing server 130 trains the machinelearning model to categorize or disregard future object acquisitions asreplacements of prior object acquisitions based on a frequency ofwarranty claims submitted in connection with the object acquisitions.For example, transaction processing server 130 may determine that theuser consistently files a warranty claim for prior object acquisitionshaving similar purchase characteristics to a recent object acquisition,such that the machine learning model may be trained to determine therecent object acquisitions do serve as replacements given a regularityof the warranty claims submitted by the user. It should be appreciatedthat transaction processing server 130 may train the machine learningmodel based on acquisition data (e.g., from purchase data repository125) and/or warranty data (e.g., from warranty data server 140) of theuser, or a plurality of users.

Still referring to FIG. 2 , and in response to determining the presentobject acquisition replaces at least one prior object acquisition atstep 212, transaction processing server 130 may be configured todetermine the coverage information corresponding to the prior objectacquisition at step 214. In other words, transaction processing server130 may determine the existence of a warranty plan associated with theprior object acquisition, and belonging to the user, by communicationwith at least one (e.g., a plurality) warranty data server 140. In thisinstance, transaction processing server 130 may determine at least onewarranty data server 140 provides coverage protection for the priorobject acquisition.

At step 216, transaction processing server 130 may determine a validityand/or status of the coverage protection provided by the warranty planfor the prior object acquisition that relates to the present objectacquisition. In response to determining the status of the coverageprotection is inactive and/or expired at step 218, transactionprocessing server 130 may be configured to end the process 200.Alternatively, transaction processing server 130 may transmit an alertto user device 105 notifying the user of the existence of the priorobject acquisition and the expired coverage protection.

In response to determining the status of the coverage protection of theprior object acquisition is active at step 218, transaction processingserver 130 may be configured to generate an alert for transmission touser device 105 at step 220. The alert may include an identification ofthe prior object acquisition that corresponds to the present objectacquisition, along with details relating to the coverage protectionprovided by the warranty plan. The alert may include a messagesuggesting utilization of the coverage protection provided by thewarranty plan for the user to seek reimbursement of value lost from thereplacement of the prior object acquisition. The alert may includecontact information for a provider of the warranty plan for the user'suse, thereby facilitating use of the existing protection. The contactinformation may include a web link directing the user to complete claimdocumentation necessary for submitting a warranty claim with thecoverage provider. The alert may further include supplemental data foruse by the user, such as statistical information relating to apercentage of success for receiving compensation from the coverageprovider for similar warranty claims by other users. Transactionprocessing server 130 may transmit the alert to user device 105 viaelectronic network 115.

At step 222, transaction processing server 130 may be configured toretrieve claim documentation from a provider of the warranty plancovering the prior object acquisition. For example, transactionprocessing server 130 may retrieve the corresponding claim documentationfrom warranty data server 140 and transmit the documentation to userdevice 105. In some embodiments, transaction processing server 130 maybe configured to autocomplete the claim documentation based oninformation relating to the prior object acquisition (e.g., acquisitiondata), the user, the coverage protection (e.g., warranty data), andmore. In this instance, transaction processing server 130 may transmitthe completed claim documentation to user device 105 for review andacceptance prior to submitting the claim documentation to the providerof the warranty plan. In other instances, transaction processing server130 may automatically submit the completed claim documentation to theprovider and provide the user a notification of the submission at userdevice 105.

Transaction processing server 130 may be further configured to determinewhether the present object acquisition (step 202) includes coverageprotection from a new warranty plan. Transaction processing server 130may supplement purchase data repository 125 with acquisition dataindicative of the present object acquisition for categorizing thepresent object acquisition in a corresponding object grouping (e.g., theobject grouping identified at step 206). Transaction processing server130 may further supplement warranty data server 140 with the acquisitiondata and/or warranty data associated with the present objectacquisition.

It should be appreciated that system 100 may be configured to generatedata (e.g., coverage information) for transmission to a user, whereinthe data may not have been previously known to the user. In thisinstance, system 100 may provide the user with new information, andfacilitate identification of the necessary tools to utilize saidinformation. Such tools may include, but are not limited to, thewarranty service provider's claim documentation, acquisition data ofprior object acquisitions for completing the claim documentation,identity and contact information of warranty service provider,statistical information relating to a percentage of success forreceiving compensation from the warranty service provider, and more.System 100 may allow for expedited processing control and speed forwarranty claims between consumers and warranty service providers. System100 may increase a volume of warranty claims submitted to warrantyservice providers by consumers. Further, by at least partiallyautomating the claim submission process, system 100 may increase apercentage of warranty claims successfully submitted to warranty serviceproviders, thereby minimizing a percentage of rejected claims forfailure to comply with required formalities (e.g., procedures, submittedinformation, timing of claim, etc.). Additionally, system 100 mayautomatically determine the necessary claim submission formalitiesand/or procedures for each of the plurality of warranty serviceproviders, such that a user of system 100 may not be required to commitan expenditure of time, resources, or effort.

FIG. 3 is a simplified functional block diagram of a computing device300 that may be configured as a device for executing the methods of FIG.2 , according to exemplary embodiments of the present disclosure. Any ofthe devices, databases (e.g., servers), processors, etc. of system 100discussed herein may be an assembly of the hardware of computing device300 including, for example, user device 105, financial institutionserver 110, merchant server 120, purchase data repository 125,transaction processing server 130, and/or warranty data server 140,according to exemplary embodiments of the present disclosure.

Computing device 300 may include a central processing unit (“CPU”) 302that may be in the form of one or more processors configured to executeprogram instructions, such as those of process 200 described in detailabove. In some embodiments, the processor(s) of CPU 302 includes both aCPU and a GPU. Computing device 300 may further include a storage unit306 that may include non-volatile memory, such as, for example, astorage media (e.g., solid-state drives), ROM, HDD, SDD, etc. Examplesof storage media include solid-state storage media (e.g., solid statedrives and/or removable flash memory), optical storage media (e.g.,optical discs), and/or magnetic storage media (e.g., hard disk drives).Storage unit 306 may store data on a computer readable medium 322. Insome embodiments, computing device 300 may receive programming and datavia network communications from electronic network 115, such as, forexample, via a communication interface 320 configured to communicatewith one or more other components of system 100.

Still referring to FIG. 3 , computing device 300 may include a memory304 that is volatile memory, such as, for example, RAM, solid-statememories, optical storage media (e.g., optical discs), magnetic storagemedia (e.g., hard disk drives), etc. Memory 304 may be configured forstoring one or more instructions 324 for executing techniques presentedherein, such as those of process 200 shown and described above. Memory304 may further include a non-transitory computer-readable medium.Therefore, whenever a computer-implemented method is described in thisdisclosure, this disclosure shall also be understood as describing anon-transitory computer-readable medium storing instructions that, whenexecuted by one or more processors (e.g., CPU 302), cause the one ormore processors to perform the computer-implemented method.

In some embodiments, the one or more instructions 324 may be storedtemporarily or permanently within other modules of computing device 300,such as, for example, CPU 302, computer readable medium 322, and more.Computing device 300 may include an input/output device 312 includingone or more input ports and one or more output ports. Input/outputdevice 312 may include, for example, a keyboard, a mouse, a touchscreen,etc. (i.e., input ports). Input/output device 312 may further include amonitor, a display, a printer, etc. (i.e. output ports). Computingdevice 300 may further include a display device 310 configured toconnect with input/output device 312. The aforementioned elements ofcomputing device 300 may be connected to one another through an internalcommunication bus 308, which represents one or more busses.

In other embodiments, the various system functions of process 200 shownin FIG. 2 may be implemented in a distributed fashion on a number ofsimilar platforms to distribute the processing load on multiplecomputing devices 300. Alternatively, the system functions may beimplemented by appropriate programming of one computer hardwareplatform, such as, for example, computing device 300.

Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of executable codeand/or associated data that is carried on or embodied in a type ofmachine-readable medium. “Storage” type media include any or all of thetangible memory of the computers, processors or the like, or associatedmodules thereof, such as various semiconductor memories, tape drives,disk drives and the like, which may provide non-transitory storage atany time for the software programming.

All or portions of the software may at times be communicated through theInternet or various other telecommunication networks. Suchcommunications, for example, may enable loading of the software from onecomputer or processor into another, for example, from a managementserver or host computer of the mobile communication network into thecomputer platform of a server and/or from a server to the mobile device.Thus, another type of media that may bear the software elements includesoptical, electrical and electromagnetic waves, such as used acrossphysical interfaces between local devices, through wired and opticallandline networks and over various air-links. The physical elements thatcarry such waves, such as wired or wireless links, optical links, or thelike, also may be considered as media bearing the software. As usedherein, unless restricted to non-transitory, tangible “storage” media,terms such as computer or machine “readable medium” refer to any mediumthat participates in providing instructions to a processor forexecution.

While the presently disclosed methods, devices, and systems aredescribed with exemplary reference to transmitting data, it should beappreciated that the presently disclosed embodiments may be applicableto any environment, such as a desktop or laptop computer. Also, thepresently disclosed embodiments may be applicable to any type ofInternet protocol. It is intended that the specification and examples beconsidered as exemplary only, with a true scope and spirit of thedisclosure being indicated by the following claims.

In general, any process discussed in this disclosure that is understoodto be performable by a computer may be performed by one or moreprocessors. Such processes include, but are not limited to, the processshown in FIG. 2 , and the associated language of the specification. Theone or more processors may be configured to perform such processes byhaving access to instructions (computer-readable code) that, whenexecuted by the one or more processors, cause the one or more processorsto perform the processes. The one or more processors may be part of acomputer system (e.g., one of the computer systems discussed above) thatfurther includes a memory storing the instructions. The instructionsalso may be stored on a non-transitory computer-readable medium. Thenon-transitory computer-readable medium may be separate from anyprocessor. Examples of non-transitory computer-readable media includesolid-state memories, optical media, and magnetic media.

It should be appreciated that in the above description of exemplaryembodiments of the invention, various features of the invention aresometimes grouped together in a single embodiment, figure, ordescription thereof for the purpose of streamlining the disclosure andaiding in the understanding of one or more of the various inventiveaspects. This method of disclosure, however, is not to be interpreted asreflecting an intention that the claimed invention requires morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive aspects lie in less than allfeatures of a single foregoing disclosed embodiment. Thus, the claimsfollowing the Detailed Description are hereby expressly incorporatedinto this Detailed Description, with each claim standing on its own as aseparate embodiment of this invention.

Furthermore, while some embodiments described herein include some butnot other features included in other embodiments, combinations offeatures of different embodiments are meant to be within the scope ofthe invention, and form different embodiments, as would be understood bythose skilled in the art. For example, in the following claims, any ofthe claimed embodiments can be used in any combination.

Thus, while certain embodiments have been described, those skilled inthe art will recognize that other and further modifications may be madethereto without departing from the spirit of the invention, and it isintended to claim all such changes and modifications as falling withinthe scope of the invention. For example, functionality may be added ordeleted from the block diagrams and operations may be interchanged amongfunctional blocks. Steps may be added or deleted to methods describedwithin the scope of the present invention.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other implementations, which fallwithin the true spirit and scope of the present disclosure. Thus, to themaximum extent allowed by law, the scope of the present disclosure is tobe determined by the broadest permissible interpretation of thefollowing claims and their equivalents, and shall not be restricted orlimited by the foregoing detailed description. While variousimplementations of the disclosure have been described, it will beapparent to those of ordinary skill in the art that many moreimplementations are possible within the scope of the disclosure.Accordingly, the disclosure is not to be restricted except in light ofthe attached claims and their equivalents.

What is claimed is:
 1. A computer-implemented method for facilitatingidentification of object coverage information using prior acquisitiondata, comprising: detecting an object acquisition; determining agrouping of the object acquisition from a plurality of groupings;identifying a corresponding object acquisition within the same groupingas the object acquisition; determining the corresponding objectacquisition includes coverage protection; and transmitting an alert ofthe corresponding object acquisition and the coverage protection.
 2. Thecomputer-implemented method of claim 1, wherein prior to determining thegrouping of the object acquisition, the method further comprises:determining whether the object acquisition is for an object associatedwith coverage protection.
 3. The computer-implemented method of claim 1,wherein prior to transmitting the alert, the method further comprises:determining a status of the coverage protection for the correspondingobject acquisition, wherein the alert is transmitted when the status ofthe coverage protection is active.
 4. The computer-implemented method ofclaim 1, wherein prior to transmitting the alert, the method furthercomprises: transmitting a verification inquiry to a user device toconfirm the object acquisition is for an object that replaces a priorobject acquired via the corresponding object acquisition; and receivingan affirmative response to the verification inquiry from the userdevice.
 5. The computer-implemented method of claim 1, furthercomprising: retrieving claim submission documentation from a coverageprovider and for the corresponding object acquisition; and transmittingthe claim submission documentation to a user device.
 6. Thecomputer-implemented method of claim 5, wherein prior to transmittingthe claim submission documentation to the user device, the methodcomprises: completing the claim submission documentation based oninformation relating to the corresponding object acquisition.
 7. Thecomputer-implemented method of claim 6, wherein prior to transmittingthe claim submission documentation to the user device, the methodcomprises: transmitting the completed claim submission documentation tothe coverage provider.
 8. The computer-implemented method of claim 1,wherein each of the plurality of groupings includes data indicative of aplurality of prior object acquisitions having one or morecharacteristics.
 9. The computer-implemented method of claim 8, whereinthe one or more characteristics includes a merchant name, an acquisitiondate, an acquisition amount, or a merchant grouping code associated witheach of the plurality of prior object acquisitions.
 10. Thecomputer-implemented method of claim 8, wherein determining the groupingof the object acquisition from the plurality of groupings comprises:comparing one or more characteristics of the object acquisition to theone or more characteristics of the plurality of prior objectacquisitions grouped in each of the plurality of groupings.
 11. Thecomputer-implemented method of claim 1, further comprising: determiningthe object acquisition includes a new coverage protection; and addingdata indicative of the object acquisition and the new coverageprotection in at least one of the plurality of groupings.
 12. Thecomputer-implemented method of claim 11, further comprising: adding oneor more characteristics of the object acquisition in the at least oneplurality of groupings.
 13. The computer-implemented method of claim 1,wherein determining the corresponding object acquisition includescoverage protection comprises: communicating with a server of amanufacturer, a payment service provider, a retail service provider, ora web platform provider; determining at least one of the manufacturer,the payment service provider, the retail service provider, or the webplatform provider provides coverage protection for the correspondingobject acquisition; and retrieving information of the coverageprotection from the server.
 14. A computer-implemented method forautomating product coverage identification, comprising: determining anoccurrence of an object acquisition; categorizing the object acquisitionto at least one category of a plurality of categories based on acharacteristic of the object acquisition; determining a prior productacquisition included within the at least one category has acorresponding characteristic similar to the characteristic of the objectacquisition; determining the prior object acquisition includes acoverage plan; and generating a notification including the prior objectacquisition and the coverage plan.
 15. The computer-implemented methodof claim 14, wherein prior to generating the notification, the methodfurther comprises: retrieving information of the coverage plan;determining a validity of the coverage plan for the prior objectacquisition; transmitting an inquiry to confirm the object acquisitionis for replacing the prior object acquisition; and transmitting thenotification in response to receiving an affirmative response to theinquiry.
 16. The computer-implemented method of claim 14, furthercomprising: submitting an automatic claim for reimbursement to acoverage provider for the prior object acquisition.
 17. Thecomputer-implemented method of claim 14, wherein categorizing the objectacquisition to the at least one category based on the characteristic ofthe object acquisition comprises: comparing the characteristic of theobject acquisition to one or more characteristics of a plurality ofprior object acquisitions categorized in each of the plurality ofcategories.
 18. The computer-implemented method of claim 14, furthercomprising: determining the object acquisition includes a new coverageplan; and storing data indicative of the object acquisition, the newcoverage plan, and the characteristic of the object acquisition in theat least one category.
 19. The computer-implemented method of claim 14,wherein prior to transmitting the notification, the method furthercomprises: determining whether the coverage plan for the correspondingobject acquisition has expired; and transmitting the notification inresponse to determining the coverage plan has not expired.
 20. A systemfor facilitating identification of existing protection for prior objectacquisitions, comprising: a processor; and a memory storing instructionsthat, when executed by the processor, causes the processor to performoperations including: receiving data indicative of an objectacquisition; determining at least one grouping of the object acquisitionfrom a plurality of groupings; identifying a matching object acquisitionin the same grouping of the object acquisition from prior objectacquisition data; determining the matching object acquisition includesobject coverage protection; and transmitting an alert to a user deviceof the matching object acquisition and the object coverage protection.